home *** CD-ROM | disk | FTP | other *** search
- Path: news.aracnet.com!news
- From: acs@aracnet.com (ACS)
- Newsgroups: comp.lang.c
- Subject: [HELP] TOOL FOR REMOVING TOO MANY #ifdef's
- Date: 15 Feb 1996 21:38:58 GMT
- Organization: aracnet.com -- Portland's loudest electrons
- Message-ID: <4g095i$ld4@cobweb.aracnet.com>
- NNTP-Posting-Host: ppp-m16.aracnet.com
- Mime-Version: 1.0
- X-Newsreader: WinVN 0.99.3
-
- Hi,
-
- I was given a huge "PORTABLE" C/C++ source code that's supposed to compile
- under DOS, Unix, Windows, etc. I am currently adding some features while
- porting the source set to Windows95. Of course I am having quite a bit of
- problems.
-
- The task of adding new features and building a new Win95 port is IMMENSELY
- exacerbated because the source set has a huge number of #ifdef's for various
- OS/Version/features builds. And frankly, I have no idea at all what some of
- these #ifdef's mean (Ex. #ifdef _PRACTICAL).
-
- What I would like to do is "SELECTIVELY PREPROCESS THE SOURCE WITHOUT
- SUBSTITUTING MACROS". This way I figure I could reduce the size of the
- source set by 50%, and make it more intellible. I tried GNU CPP, but I could
- not find a way "NOT TO SUBSTITUTE MACROS".
-
- Could anyone point me to a tool that does
- "SELECTIVELY PREPROCESS THE SOURCE WITHOUT SUBSTITUTING MACROS"
-
- Thanks, Adrian
-
-